Method and system for optimizing the feedback mechanism in data link layer

ABSTRACT

Accordingly the embodiments herein provide a for providing a Radio Link Control (RLC) status report based on a configuration of a Packet Data Convergence Protocol (PDCP) entity of a User Equipment (UE) in a wireless network system. The method comprises detecting, at the UE, that a RLC layer is configured to an Acknowledge Mode (AM), informing, at the UE, a t-reordering timer from the PDCP entity of the UE to a RLC entity of the UE, receiving, at the UE, a first Packet Data unit (PDU) by the entity and at least one second PDU by the RLC entity, detecting, by the UE, a PDU gap when the first PDU and the second PDU are not consecutive; providing, by the UE, the RLC status report to a transmitter side of the RLC entity of a network to recover packets missed in the PDU gap based on the t-reordering timer, and recovering, by the network, the packets based on the RLC status report.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is based on and claims priority under 35 U.S.C. § 119to Indian Patent Application No. 201841025681 filed on Jul. 10, 2018 andIndian Patent Application No. 201841025681 filed on Jul. 9, 2019, thedisclosures of which are incorporated by reference herein in theirentireties.

BACKGROUND 1. Field

The present disclosure relates to configuration of Acknowledgment Mode(AM) Data Radio Bearer (DRB) in data link layer in 5^(th) Generation(5G) networks and more specifically to a method and system for providingRadio Link Control (RLC) status report based on a configuration ofPacket Data Convergence Protocol (PDCP) layer in the 5G network.

2. Description of Related Art

To meet the demand for wireless data traffic having increased sincedeployment of 4G communication systems, efforts have been made todevelop an improved 5G or pre-5G communication system. Therefore, the 5Gor pre-5G communication system is also called a ‘Beyond 4G Network’ or a‘Post LTE System’. The 5G communication system is considered to beimplemented in higher frequency (mmWave) bands, e.g., 60 GHz bands, soas to accomplish higher data rates. To decrease propagation loss of theradio waves and increase the transmission distance, the beamforming,massive multiple-input multiple-output (MIMO), Full Dimensional MIMO(FD-MIMO), array antenna, an analog beam forming, large scale antennatechniques are discussed in 5G communication systems. In addition, in 5Gcommunication systems, development for system network improvement isunder way based on advanced small cells, cloud Radio Access Networks(RANs), ultra-dense networks, device-to-device (D2D) communication,wireless backhaul, moving network, cooperative communication,Coordinated Multi-Points (CoMP), reception-end interference cancellationand the like. In the 5G system, Hybrid FSK and QAM Modulation (FQAM) andsliding window superposition coding (SWSC) as an advanced codingmodulation (ACM), and filter bank multi carrier (FBMC), non-orthogonalmultiple access (NOMA), and sparse code multiple access (SCMA) as anadvanced access technology have been developed.

The Internet, which is a human centered connectivity network wherehumans generate and consume information, is now evolving to the Internetof Things (IoT) where distributed entities, such as things, exchange andprocess information without human intervention. The Internet ofEverything (IoE), which is a combination of the IoT technology and theBig Data processing technology through connection with a cloud server,has emerged. As technology elements, such as “sensing technology”,“wired/wireless communication and network infrastructure”, “serviceinterface technology”, and “Security technology” have been demanded forIoT implementation, a sensor network, a Machine-to-Machine (M2M)communication, Machine Type Communication (MTC), and so forth have beenrecently researched. Such an IoT environment may provide intelligentInternet technology services that create a new value to human life bycollecting and analyzing data generated among connected things. IoT maybe applied to a variety of fields including smart home, smart building,smart city, smart car or connected cars, smart grid, health care, smartappliances and advanced medical services through convergence andcombination between existing Information Technology (IT) and variousindustrial applications.

In line with this, various attempts have been made to apply 5Gcommunication systems to IoT networks. For example, technologies such asa sensor network, Machine Type Communication (MTC), andMachine-to-Machine (M2M) communication may be implemented bybeamforming, MIMO, and array antennas. Application of a cloud RadioAccess Network (RAN) as the above-described Big Data processingtechnology may also be considered to be as an example of convergencebetween the 5G technology and the IoT technology.

SUMMARY

The principal object of the embodiments herein is to provide a RLCstatus report based on a configuration of the PDCP entity in a wirelessnetwork system.

Another object of the embodiment herein is informing a RLC entity abouta t-reordering timer by the PDCP entity of the UE.

Another object of the embodiment herein is to providing the RLC statusreport to recover or discard the PDU missed in the gap based on thet-reordering timer.

Another object of the embodiment herein is to generate the RLC statusreport by sending NAK message in the status report, only if the PDU isnot received within duration of twice the t-reordering time.

Another object of the embodiment herein is to generate the RLC statusreport by sending ACK message in the status report, if the PDU is notreceived after the duration of twice the t-reordering time.

Accordingly the invention provides a method and system for providing aRLC status report based on a configuration of a PDCP entity in awireless network system. The method comprises detecting at a UE that, anAM Data Radio Bearer (DRB) is configured. The UE comprises a RLC entitywhich is a receiver side of the RLC layer. Further the network comprisesa transmitter side of the RLC entity. The method further comprisesinforming, at the UE a t-reordering time from the PDCP entity of the UEto a RLC entity of the UE. The method further comprises providing by atransmitter side of the RLC entity a RLC status report to a receiverside of the RLC entity to recover or discard the packets missed in thePDU gap based on the t-reordering timer. The method also comprisesreceiving by the UE the PDU based on the RLC status report based on PDCPconfiguration and the RLC status report.

In another embodiment a method for packet transmission between a firstlayer and a second layer in a network comprises receiving, by the firstlayer, at least one first data packet from a transmitting terminal(entity), detecting, by the first layer, that a preceding data packet isyet to be received and starting a first timer and sending, by the firstlayer, the at least one first packet to the second layer and detectingthe duration of a second timer at the second layer. The method alsoincludes receiving, by the first layer, a second packet from thetransmitting terminal (entity), wherein the second packet has a sequencenumber greater than the first data packet; and sending, by the firstlayer, a status report to the transmitting terminal (entity) on at leastone of the expiry of the first timer or a request from the transmittingterminal (entity) based on the second timer.

In an embodiment the t-reordering timer is sent by the network to theUE. Further providing, by the UE, the RLC status report to a transmitterside of the RLC entity of a network to recover packets missed in the PDUgap based on the t-reordering timer comprises: performing at least oneof: sending a Non-Acknowledgement (NAK) message in the RLC status reportto the RLC entity of the UE, if the data packet is not received within aduration of twice the t-reordering timer; and sending a Acknowledgement(ACK) message in the RLC status report to the RLC entity of the UE, evenif the data packet is not received after twice the t-reordering timer.In an embodiment wherein the transmitting terminal (entity) is atransmitting side of the first layer present in the network

In another embodiment recovering, by the network, the packets based onthe RLC status report comprises re-transmitting the PDU with aNon-Acknowledgement (NAK) message in the RLC status report; and ignoringthe PDU with a Acknowledgement (ACK) message in the RLC status report.

In another embodiment a RLC window is moved forward, when the datapacket is not received after twice the t-reordering timer.

In another embodiment wherein the PDCP entity (602) waits for durationof twice the t-reordering timer for receiving the PDU with the NACKmessage in the RLC status report.

Accordingly the embodiments herein provide a wireless network systemcomprising a UE. The UE further comprises a memory, a processor and acommunicator. The processor further comprises a RLC entity and a PDCPentity. to detect that a RLC layer is configured to an Acknowledge Mode(AM) and inform a t-reordering timer from the PDCP entity to a RLCentity; receive a first Packet Data unit (PDU) by the RLC entity and atleast one second PDU by the RLC entity; detect a PDU gap when the firstPDU and the second PDU are not consecutive; and provide the RLC statusreport to a transmitter side of the RLC entity of the network to recoverpackets missed in the PDU gap based on the t-reordering timer; and

-   -   receive the packets based on the RLC status report The RLC        entity comprises a reassembly timer and a RLC status report        generator and a recover engine. The PDCP entity comprises a        reordering timer. In an embodiment the UE detects that a AM DRB        is configured. The PDCP entity informs the RLC entity of the UE        about t-reordering time duration. The RLC entity transmitter        side provides a status report to the RLC entity receiver side        based on the t-reordering time.

These and other aspects of the embodiments herein will be betterappreciated and understood when considered in conjunction with thefollowing description and the accompanying drawings. It should beunderstood, however, that the following descriptions, while indicatingpreferred embodiments and numerous specific details thereof, are givenby way of illustration and not of limitation. Many changes andmodifications may be made within the scope of the embodiments hereinwithout departing from the spirit thereof, and the embodiments hereininclude all such modifications.

Before undertaking the DETAILED DESCRIPTION below, it may beadvantageous to set forth definitions of certain words and phrases usedthroughout this patent document: the terns “include” and “comprise,” aswell as derivatives thereof, mean inclusion without limitation; the term“or,” is inclusive, meaning and/or; the phrases “associated with” and“associated therewith,” as well as derivatives thereof, may mean toinclude, be included within, interconnect with, contain, be containedwithin, connect to or with, couple to or with, be communicable with,cooperate with, interleave, juxtapose, be proximate to, be bound to orwith, have, have a property of, or the like; and the term “controller”means any device, system or part thereof that controls at least oneoperation, such a device may be implemented in hardware, firmware orsoftware, or some combination of at least two of the same. It should benoted that the functionality associated with any particular controllermay be centralized or distributed, whether locally or remotely.

Moreover, various functions described below can be implemented orsupported by one or more computer programs, each of which is formed fromcomputer readable program code and embodied in a computer readablemedium. The terms “application” and “program” refer to one or morecomputer programs, software components, sets of instructions,procedures, functions, objects, classes, instances, related data, or aportion thereof adapted for implementation in a suitable computerreadable program code. The phrase “computer readable program code”includes any type of computer code, including source code, object code,and executable code. The phrase “computer readable medium” includes anytype of medium capable of being accessed by a computer, such as readonly memory (ROM), random access memory (RAM), a hard disk drive, acompact disc (CD), a digital video disc (DVD), or any other type ofmemory. A “non-transitory” computer readable medium excludes wired,wireless, optical, or other communication links that transporttransitory electrical or other signals. A non-transitory computerreadable medium includes media where data can be permanently stored andmedia where data can be stored and later overwritten, such as arewritable optical disc or an erasable memory device.

Definitions for certain words and phrases are provided throughout thispatent document, those of ordinary skill in the art should understandthat in many, if not most instances, such definitions apply to prior, aswell as future uses of such defined words and phrases.

BRIEF DESCRIPTION OF THE DRAWINGS

This invention is illustrated in the accompanying drawings, throughoutwhich like reference letters indicate corresponding parts in the variousfigures. The embodiments herein will be better understood from thefollowing description with reference to the drawings, in which:

FIGS. 1-4 are time diagrams illustrating an example scenario for windowmovement at data link layer using conventional methods, according to theprior art;

FIG. 5 is a block diagram of a UE 500 for providing a RLC status reportbased on a configuration of a PDCP entity, according to the prior art;

FIG. 6 depicts a block of the processor 520 for recovering PDU at theRLC entity, according to an embodiment as disclosed herein; and

FIG. 7 and FIG. 8 are schematic diagrams illustrating the proposedmethod with example embodiments, according to an embodiment as disclosedherein.

FIG. 9 is a block diagram of the network entity 900, according to anembodiment as disclosed herein.

DETAILED DESCRIPTION

FIGS. 1 through 9, discussed below, and the various embodiments used todescribe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way to limit the scope of the disclosure. Those skilled in the artwill understand that the principles of the present disclosure may beimplemented in any suitably arranged system or device

The embodiments herein and the various features and advantageous detailsthereof are explained more fully with reference to the non-limitingembodiments that are illustrated in the accompanying drawings anddetailed in the following description. Descriptions of well-knowncomponents and processing techniques are omitted so as to notunnecessarily obscure the embodiments herein. Also, the variousembodiments described herein are not necessarily mutually exclusive, assome embodiments can be combined with one or more other embodiments toform new embodiments. The term “or” as used herein, refers to anon-exclusive or, unless otherwise indicated. The examples used hereinare intended merely to facilitate an understanding of ways in which theembodiments herein can be practiced and to further enable those skilledin the art to practice the embodiments herein. Accordingly, the examplesshould not be construed as limiting the scope of the embodiments herein.

As is traditional in the field, embodiments may be described andillustrated in terms of blocks which carry out a described function orfunctions. These blocks, which may be referred to herein as managers,units, modules, hardware components or the like, are physicallyimplemented by analog and/or digital circuits such as logic gates,integrated circuits, microprocessors, microcontrollers, memory circuits,passive electronic components, active electronic components, opticalcomponents, hardwired circuits and the like, and may optionally bedriven by firmware and software. The circuits may, for example, beembodied in one or more semiconductor chips, or on substrate supportssuch as printed circuit boards and the like. The circuits constituting ablock may be implemented by dedicated hardware, or by a processor (e.g.,one or more programmed microprocessors and associated circuitry), or bya combination of dedicated hardware to perform some functions of theblock and a processor to perform other functions of the block. Eachblock of the embodiments may be physically separated into two or moreinteracting and discrete blocks without departing from the scope of thedisclosure. Likewise, the blocks of the embodiments may be physicallycombined into more complex blocks without departing from the scope ofthe disclosure.

in New Radio (NR), it has been agreed to follow a unified re-orderingscheme for Data and Signaling radio bearers DRB(s)/SRB(s) inUnacknowledged Mode (UM) and Acknowledged Mode (AM) in a PDCP layer. Dueto this, for a DRB configured in AM mode, there arises a problem ofpacket getting discarded at the PDCP layer if the packet is receivedfrom RLC layer (due to packet received after multiple NACKsre-transmissions at RLC) after the PDCP window movement. This PDCPwindow movement is performed at expiry of t-reordering timer. Thet-reordering timer is used by the receiving side of a PDCP entity andreceiving PDCP entity in order to detect loss of PDUs.

FIGS. 1-4 are schematic diagrams illustrating the conventional method ofwindow movement in data link layer. As seen in FIG. 1 the RLC layer senddata packets to the PDCP layer. The RCL layer comprises a transmitterside and a receiver side. The receiver side of the RLC layer is presentin a UE and the transmitter side of the RLC layer is at the network (forexample, network entity (node) in the network (e.g. base station)).

As seen in FIG. 1, at time T0 the receiver side of the RLC layerreceives a data packet with Sequence Number (SN) 0 from the transmitterside of the RLC layer in the network and immediately forwards it to thePDCP layer. At RLC layer receiver side the value of Rx_Next is theexpected count value of receiving next data packet from the lower layerswhich is 1 in the current example. The value of Rx_Next_Status_triggeris the SN which triggered t-reassembly timer. The value ofRx_Highest_Status is the count of the Maximum STATUS transmit statevariable in RLC layer which is 1 in the current example. At PDCP thevalue of Rx_Next is the expected count value of receiving next datapacket from the lower layers which is 1 in the current example. Thevalue of Rx_Deliv is the COUNT value of the first PDCP packet notdelivered to the upper layers, but still waited for, which is also 1 inthe current example. The value of Rx_reorder (Rx_Reord) is the value ofcount which triggers the t-reordering timer.

As seen in FIG. 2, at T1, the RLC layer receiver side receives anotherdata packet with SN 5 and a t-reassembly timer is started at the RLClayer receiver side as data packets with SN 1-4 are not received by theRLC layer. The RLC layer receiver side pushes the data packet with SN 5to the PDCP. At PDCP a t-reordering timer has started since there is gapbetween the data packet received as data packets with SN 1-4 are notreceived by the PDCP layer. The time duration of t-reordering timer isprovided to a UE by the network. At PDCP when the t-reordering timerduration is expired, then the lower bound of the PDCP window is movedforward. However, the RLC is in AM mode and the lower bound at the RLCis not changed.

As seen in FIG. 3, at T2, the RLC layer receiver side receives anotherdata packet with SN 6, 7 and 9, and sends the data packets to the PDCP,while the T-reassembly timer is still running. The RLC layer receiverside may send a RLC status report to the RLC transmitter side.

In FIG. 4, at T3, the RLC layer receiver side is in AM mode, and the RLCwindow is still not moved and hence the UE still send the status reportuntil the packets with SN 1-4 are received. The PDCP received thepackets with SN 1-4 from the RLC but at PDCP, the lower bound of thewindow is 8, and hence the PDCP ignore the data packets sent by the RLChaving SN as 1-4. Thus there is wastage of resource and unnecessaryprocessing is done by the UE, asking for data packets with SN 1-4.

Thus, it is desired to address the above mentioned problems and at leastprovide a useful alternative for indicating change in the dualcapability of the UE.

The embodiments herein disclose a method for providing a RLC statusreport based on a configuration of a PDCP entity in a wireless networksystem. The method comprises detecting at a UE that, an AM Data RadioBearer (DRB) is configured. The UE comprises a RLC entity which is areceiver side of the RLC layer. Further the network comprises atransmitter side of the RLC entity. The method further comprisesinforming, at the UE a t-reordering time from the PDCP entity of the UEto a RLC entity of the UE. The method further comprises providing by atransmitter side of the RLC entity a RLC status report to a receiverside of the RLC entity to recover or discard the packets missed in thePDU gap based on the t-reordering timer. The method also comprisesreceiving by the UE the PDU based on the RLC status report based on PDCPconfiguration and the RLC status report.

In another embodiment a method for packet transmission between a firstlayer and a second layer in a network comprises receiving, by the firstlayer, at least one first data packet from a transmitting terminal(entity), detecting, by the first layer, that a preceding data packet isyet to be received and starting a first timer and sending, by the firstlayer, the at least one first packet to the second layer and detectingthe duration of a second timer at the second layer. The method alsoincludes receiving, by the first layer, a second packet from thetransmitting terminal (entity), wherein the second packet has a sequencenumber greater than the first data packet; and sending, by the firstlayer, a status report to the transmitting terminal (entity) on at leastone of the expiry of the first timer or a request from the transmittingterminal (entity) based on the second timer.

Referring now to the drawings, and more particularly to FIGS. 5 through8, where similar reference characters denote corresponding featuresconsistently throughout the figures, there are shown preferredembodiments.

FIG. 5 is a block diagram of the UE 500 for providing a RLC statusreport based on a configuration of the PDCP entity. The UE 500 comprisesa memory 510, a processor 520 and a communicator 530.

The processor 520 is coupled with the memory 510 and is configured toexecute the instructions stored in the memory 510. The memory 510 mayinclude non-volatile storage elements. Examples of such non-volatilestorage elements may include magnetic hard discs, optical discs, floppydiscs, flash memories, or forms of an Erasable Programmable Memory(EPROM) or an Electrically Erasable and Programmable Read Only Memory(EEPROM).

In addition, the memory 510 may, in some examples, be considered anon-transitory storage medium. The term “non-transitory” may indicatethat the storage medium is not embodied in a carrier wave or apropagated signal. However, the term “non-transitory” should not beinterpreted that the memory 520 is non-movable. In some examples, thememory 510 can be configured to store larger amounts of information thanthe memory 510. In certain examples, a non-transitory storage medium maystore the data that can, over time, change (e.g., in Random AccessMemory (RAM) or cache).

The communicator 530 is configured to communicate internally betweenhardware components in the UE 500.

In an embodiment the wireless network system comprises the UE 500including the processor 520 for providing the RLC status report by thereceiver side of the RLC entity to the transmitter side of the RLCentity based on a t-reordering tune duration of the PDCP entity.

FIG. 6 depicts a block of the processor 520 for recovering PDU at theRLC entity. As seen in FIG. 6, the processor 520 comprises a PDCP entity602 and a RLC entity 608. The PDCP entity 602 relates to a PDCP layerpresent in the UE. The RLC entity 608 relates to a RLC layer present inthe UE 500. The RLC entity 608 is the receiver side of the RLC layerpresent in the UE. The transmitter side of the RLC layer is at thenetwork. The PDCP entity 602 comprises a t-reordering timer 604. The RLCentity 608 comprises a t-reassembly timer 610. The RLC entity 608 alsocomprises a RLC status report generator 612.

In an embodiment the wireless network system sends t-reordering timerduration to the PDCP entity 602. In an embodiment the UE 500 present inthe wireless network system detects that a Data Radio bearer (DRB) iseither configured or reconfigured. Once the DRB is configured, the PDCPentity 602 informs the RLC entity 608 about the t-reordering timerduration. At the UE 500, the PDCP entity 602 receives PDUs from the RLCentity 608. The RLC entity 608 receives the PDUs from the lower layersand forwards it to the PDCP entity 602. The PDUs received by the RLCentity 602 from the lower layers may not be in sequence. At RLC entity,if the PDUs received are not in sequence then the t-reassembly timer 610is started by the RLC entity 608. Similarly at PDCP entity 602 if thePDUs received are not in sequence then the t-reordering timer 604 isstarted by the PDCP entity 602 as there is a PDU gap. The triggering ofthe t-reordering timer 604 at the PDCP entity 602 is detected by the RLCentity 608. Upon detection of the triggering of the t-reordering timer604 by the PDCP entity 602, the RLC status report generator 612generates the RLC status report based on the t-reordering timerduration.

In an embodiment, the RLC status report is send to the transmitter sideof the RLC layer at the network. Based on the RLC status report, thetransmitter side of the RLC layer sends or ignores the data packets tothe receiver side of the RLC layer present at the UE.

The RLC status report comprises information about PDUs missed by the RLCentity 608. If a PDU which was missed in the PDU gap is not received bythe RLC entity 608, then the RLC entity 608 waits for duration of 2times the t-ordering time. If the missed PDU is still not received thenthe RLC entity 608 ignores the missed PDU and sends a positiveacknowledged message (ACK) for the particular missed PDU in the statusreport to its peer entity (for example, network entity (e.g. basestation)). Whereas RLC recovers the missed PDU and sends anunacknowledged message (NAK) for the particular missed PDU in the statusreport to its peer entity before expiry of twice the t-reordering time.Thus the RLC entity 608 send the status report containing details aboutthe missed PDUs to the RLC entity present at the network (not show infigs).

In yet another embodiment, whenever the t-reordering timer is startedand expired, the PDCP entity 602 moves the PDU window by incrementingthe window limits. This change in window at the PDCP entity 602 is sentto the RLC entity 608 such that the RLC entity is aware of the PDUs thatwill accepted by the PDCP entity 602. After receiving the window statusinformation from the PDCP entity 602, the RLC entity 608 generates theRLC status report. While generating the RLC status report, the RLCentity at the network ignores the PDU which have lower sequence numberthan the sequence number of the window at the PDCP entity 608, and sendsan acknowledged message (ACK) for the particular PDU in the statusreport to the RLC layer transmitter side at the network. Whereas the RLCentity at the network recovers the PDU which have higher sequence numberthan the sequence number of the window at the PDCP entity 608, and sendsan unacknowledged message (NAK) for the particular PDU in the statusreport to its peer entity.

FIG. 7 is a schematic diagram, illustrating the proposed method withexample embodiments. As seen in FIG. 7 the RLC entity 608 receives PDUfrom the lower layers and sends them to the PDCP entity 602. At time T0PDU 35 is received by the RLC entity 608 and is forwarded to the PDCPentity 602. At T1 PDU 38 and 39 and 40 are received by the RLC entity608. Since there is a gap between the PDUs received by the RLC entity608, the re-assembly timer 610 is started. The RLC entity 608 now waitsfor time duration of twice the t-reordering time for receiving themissed PDU 36 and 37. Here the PDU 36 and 37 are not received till twicethe t-reordering time and hence then the RLC entity 608 sends anacknowledged message (ACK) for the PDU 36 and 37 in the status report tothe RLC layer transmitter side. At time T2, even if the RLC entity 608receives missed PDU 36 and 37, the PDCP entity 602 will not accept waitfor them as the missed PDU 36 and 37 are out of window. Thus the timeand efforts from the PDCP entity 602 are saved.

FIG. 8 is a schematic diagram, illustrating the proposed method withexample embodiments. At time T0 the RLC entity 608 receives a PDU 0 fromthe RLC layer transmitter side in the network and immediately forwardsit to the PDCP entity 602. At time T1, the RLC entity 608 receives PDUs5, 6 and 7 from the RLC layer transmitter side in the network andimmediately forwards it to the PDCP entity 602. However the t-reorderingtimer 604 has started at the PDCP entity 602 since there is a gap in thePDU. After the expiry of the t-reordering timer 604, the lower bound ofPDU is moved to 8. The PDCP entity now informs the RLC entity 608 aboutthe change in the status of the window. As per proposed solution afterreceiving notification from PDCP entity 602, the RLC entity 608 updatesthe RLC receiver state variables. The RLC entity 608 while sending thestatus report to RLC layer transmitter side sends ACK message for thePDU below the lower bound of the PDCP entity 602.

Thus using the proposed method, the time and resources are saved asdiscussed above.

FIG. 9 is a block diagram of the network entity 900. The network entity900 comprises a memory 910, a processor 920 and a communicator 930.

The processor 920 is coupled with the memory 910 and is configured toexecute the instructions stored in the memory 910. The memory 910 mayinclude non-volatile storage elements. Examples of such non-volatilestorage elements may include magnetic hard discs, optical discs, floppydiscs, flash memories, or forms of an Erasable Programmable Memory(EPROM) or an Electrically Erasable and Programmable Read Only Memory(EEPROM).

In addition, the memory 910 may, in some examples, be considered anon-transitory storage medium. The term “non-transitory” may indicatethat the storage medium is not embodied in a carrier wave or apropagated signal. However, the term “non-transitory” should not beinterpreted that the memory 920 is non-movable. In some examples, thememory 910 can be configured to store larger amounts of information thanthe memory 910. In certain examples, a non-transitory storage medium maystore the data that can, over time, change (e.g., in Random AccessMemory (RAM) or cache).

The communicator 930 is configured to communicate internally betweenhardware components in the network entity 900.

In an embodiment the wireless network system comprises the networkentity 900 communicating with the UE 500 including the processor 520 forproviding the RLC status report by the receiver side of the RLC entityto the transmitter side of the RLC entity based on a t-reordering timeduration of the PDCP entity. In an embodiment, the network entity 900may be an entity (transmitting entity) including a transmitter side ofthe RLC layer. For example, the network entity 900 may be a basestation.

The embodiments disclosed herein can be implemented through at least onesoftware program running on at least one hardware device and performingnetwork management functions to control the elements.

The foregoing description of the specific embodiments will so fullyreveal the general nature of the embodiments herein that others can, byapplying current knowledge, readily modify and/or adapt for variousapplications such specific embodiments without departing from thegeneric concept, and, therefore, such adaptations and modificationsshould and are intended to be comprehended within the meaning and rangeof equivalents of the disclosed embodiments. It is to be understood thatthe phraseology or terminology employed herein is for the purpose ofdescription and not of limitation. Therefore, while the embodimentsherein have been described in terms of preferred embodiments, thoseskilled in the art will recognize that the embodiments herein can bepracticed with modification within the spirit and scope of theembodiments as described herein.

Although the present disclosure has been described with variousembodiments, various changes and modifications may be suggested to oneskilled in the art. It is intended that the present disclosure encompasssuch changes and modifications as fall within the scope of the appendedclaims

What is claims is:
 1. A method for providing a Radio Link Control (RLC)status report based on a configuration of a Packet Data ConvergenceProtocol (PDCP) entity of a User Equipment (UE) in a wireless networksystem, the method comprising: detecting, at the UE, that a RLC layer isconfigured to an Acknowledge Mode (AM); informing, at the UE, at-reordering timer from the PDCP entity of the UE to a RLC entity of theUE; receiving, at the UE, a first Packet Data unit (PDU) by the RLCentity and at least one second PDU by the RLC entity; detecting, by theUE, a PDU gap when the first PDU and the second PDU are not consecutive;providing, by the UE, the RLC status report to a transmitter side of theRLC entity of a network to recover packets missed in the PDU gap basedon the t-reordering timer; and receiving, by the UE, the packets basedon the RLC status report.
 2. The method of claim 1, wherein thet-reordering timer is sent by the network to the UE.
 3. The method ofclaim 1, wherein providing, by the UE, the RLC status report to atransmitter side of the RLC entity of a network to recover packetsmissed in the PDU gap based on the t-reordering timer comprises:performing at least one of: sending a Non-Acknowledgement (NAK) messagein the RLC status report to the RLC entity of the UE, if the data packetis not received within a duration of twice the t-reordering timer; andsending a Acknowledgement (ACK) message in the RLC status report to theRLC entity of the UE, even if the data packet is not received aftertwice the t-reordering timer.
 4. The method of claim 1, whereinrecovering, by the network the packets based on the RLC status reportcomprises: re-transmitting the PDU with a Non-Acknowledgement (NAK)message in the RLC status report; and ignoring the PDU with aAcknowledgement (ACK) message in the RLC status report.
 5. The method ofclaim 2, wherein a RLC window is moved forward, when the data packet isnot received after twice the t-reordering timer.
 6. The method of claim2, wherein the PDCP entity waits for duration of twice the t-reorderingtimer for receiving the PDU with the NACK message in the RLC statusreport.
 7. A method for packet transmission between a first layer and asecond layer in a network comprising: receiving, by the first layer, atleast one first data packet from a transmitting entity; detecting, bythe first layer, that a preceding data packet is yet to be received andstarting a first timer; sending, by the first layer, the at least onefirst packet to the second layer and detecting a duration of a secondtimer at the second layer; receiving, by the first layer, a secondpacket from the transmitting entity, wherein the second packet has asequence number greater than the first data packet; and sending, by thefirst layer, a status report to the transmitting entity on at least oneof an expiry of the first timer or a request from the transmittingentity based on the second timer.
 8. The method of claim 7, wherein thetransmitting entity is a transmitting side of the first layer present inthe network.
 9. The method of claim 7, wherein detection, by the firstlayer and the second layer, is done by analyzing a header of the atleast one received packet.
 10. The method of claim 7, wherein the firstlayer is in first Acknowledged mode (AM).
 11. The method of claim 7,wherein the first layer represents a RLC entity and the second layerrepresents a PDCP entity.
 12. The method as claimed in claim 7, whereinthe first timer is a Reassembly timer.
 13. The method as claimed inclaim 7, wherein the second time is a t-reordering timer.
 14. The methodof claim 7, wherein the first data packet and the second data packet arenot consecutive.
 15. The method as claimed in claim 7, wherein thestatus report marks the data packets as received if the data packets arenot received even after twice the duration of the second timer.
 16. A UEfor packet transmission between a first layer and a second layer,wherein the UE comprises: a memory; a processor; and a communicator,wherein the processor is coupled to the memory and the communicator, andwherein the processor is configured to: detect that a RLC layer isconfigured to an Acknowledge Mode (AM); inform a t-reordering timer fromthe PDCP entity to a RLC entity; receive a first Packet Data unit (PDU)by the RLC entity and at least one second PDU by the RLC entity; detecta PDU gap when the first PDU and the second PDU are not consecutive; andprovide the RLC status report to a transmitter side of the RLC entity ofthe network to recover packets missed in the PDU gap based on thet-reordering timer; and receive the packets based on the RLC statusreport.
 17. The UE as claimed in claim 16, wherein the t-reorderingtimer is sent by the wireless network system to the UE.
 18. The UE asclaimed in claim 16, wherein provide the RLC status report to thetransmitter side of the RLC entity comprises, perform by the receiverside of the RLC entity at least one of: send a NAK message in the RLCstatus report to the transmitter side of the RLC entity, if the datapacket is not received within a duration of twice the t-reordering time;and send an ACK message in the RLC status report to the transmitter sideof the RLC entity, even if the data packet is not received after twicethe t-reordering time.
 19. The UE as claimed in claim 16, whereinrecover the PDU based on the RLC status report comprises: re-transmit,by the transmitting side RLC entity, the PDU with NACK message in theRLC status report; and ignore by the transmitting side RLC entity, thePDU with ACK message in the RLC status report.
 20. A UE for packettransmission between a first layer and a second layer, wherein the UEcomprises: a memory; a processor; and a communicator, wherein theprocessor is coupled to the memory and the communicator; and wherein theUE comprises a first layer and a second layer, and wherein the firstlayer is configured to: receive at least one first data packet from atransmitting terminal (entity); detect that a preceding data packet isyet to be received and start a first timer; send the at least one firstpacket to the second layer and detect a duration of a second timer atthe second layer; receive a second packet from the transmitting terminal(entity), wherein the second packet has a sequence number greater thanthe first data packet; and send a status report to the transmittingterminal (entity) after an expiry of the first timer based on the secondtimer.